Response

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Subject:

Response

It's similar to the Technote, but that would be a harder one to fix. Since CA is handling the stamping of the certificate, there's a latency between the time where the certificate is created and when it will be signed by CA. In the interim, the client switches to the ID containing the unsigned certificate, which then leads to the error you are seeing. I'll create an SPR for it, but that might be a limitation of the feature. However, note that this should not impact whether or not the ID can be harvested from the client. You can also register the user without CA, which should work if you've implemented the workarounds in the Technote.

Feedback response number WEBB7NHTPL created by ~Manny Feztoomarikle on 01/21/2009